You will do demonstrations of your working project at the end of Sprints 1, 2 and 3. These demos will prepared by your team in advance and either be given during class time to an audience (possibly your instructor, student course assistant(s) or peers) and/or previously pre-recorded.

Your instructor may have you use the team/breakoutrooms or stay in the classroom (and/or have the team record the demos and submit mp4 files to myCourses as well as a link to the video uploaded to youtube - check with your instructor!). Given the number of teams in your section and availability of a course assistant, you must plan on the length of your demo to be only between10-12 minutes to demonstrate your project implementation and allow for questions. All teammates are expected to participate.

While grading your sprint submission, your instructor will also run the application to test its functionality.

We cannot stress this enough, get clarification from your instructor/client in advance so you know exactly what is expected from your team and you are not scrambling to prepare or violating the time allotment.

Sprint 3 Demonstration - MVP and 10% Feature enhancement(s)

You will use your acceptance test plan to drive the demos, so the team must ensure that it is up-to-date for the sprint submission, and clearly indicates the user stories that were implemented in each sprint and the acceptance criteria for each story.

This demonstration will have a lot of functionality to show. It will be all of the minimum viable product (MVP) and the bugfree 10% Feature enhancement(s) that you implemented. Since the time may be as short as 12 minutes, you most likely will have to setup in advance multiple demonstration scenarios running on more than one machine to be able to show all of the features in the time allocated.

The following MVP features should be part of your final demonstration.